[WIP] Technology Stack docs #551
Open
+152
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bourque
requested review from
sdhoyt,
greglucas,
subagonsouth,
tech3371,
vmartinez-cu,
bryan-harter,
laspsandoval and
maxinelasp
sdhoyt
approved these changes
May 9, 2024
| everything is written in Python. Python was chosen mostly because at the time of | ||
| development, it was the most widely used and supported language for scientific | ||
| software development, and the main programming language used within the | ||
| Datasystems group at LASP. |
…processing into technology-stack-docs
greglucas
added
the
Repo: Documentation
maxinelasp
approved these changes
May 23, 2024
| <https://smd-cms.nasa.gov/wp-content/uploads/2023/08/smd-information-policy-spd-41a.pdf>`_, | ||
| this open-source collaborative GitHub solution made the most sense. | ||
|
|
||
| Poetry |
There was a problem hiding this comment.
Maybe link to the existing poetry docs?
vmartinez-cu
approved these changes
May 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
Overview
This PR adds a new page to our documentation that describes the "technology stack" we are using to do our work, along with some words on why we chose those tools/libraries, and what other ones we may have considered. I am using the term "technology stack" here but I am definitely open to other suggestions on what to name this page.
This is currently a WIP, and I would like some help filling out some of these sections, as others probably have more insight into some of these than I do. For the sections I have filled out, I made some assumptions in them so it would be good for others to make sure those assumptions are valid!
Also, I changed the name of the parent directory that housed a bunch of docs from
development-guideto justdevelopmentto be consistent with how we were calling it in the docs themselves.